I have an issue after setting up a new Exchange 2007 installation It is a simple install. We have a firewall pointing at the edge server using Nat to direct mail from an external DNS We have a HUB server subscribed to the edge server and all of our accepted domains are entered into the HUB server. We can send outgoing mail to the internet and send internal email through the HUB server. We cannot recieve mail from the internet. The mail makes it into the Submission Queue and then I get the error. "a local loop was detected" The properites are as follows: Identity: mail\Submission\68Subject: testInternet Message ID: <From Yahoo.com for testing>From Address: SenderStatus: RetrySize (KB): 5Message Source Name: SMTP: Default internal receive connector MAILSource IP: <our External IP>SCL: 5Date Received: 11/5/2008 11:59:09 AMExpiration Time: 11/7/2008 11:59:09 AMLast Error: A local loop was detected.Queue ID: mail\SubmissionRecipients: user@ourdomain.com I am not sure what I need to do to resolve this issue. any help would be appreciated.

Hi, Check the connector and have a look where it wants to send the message to. If you typed in a DNS name of a server please check the dns-record maybe it points to a wrong IP which can cause this issue. For excluding this change the dns name to the ip-address of the HUB Server. Regards, Johan blog: www.johanveldhuis.nl

The firewall is pointing straight at the edge server, the receive connector is accepting mail from anyone, the edge server is synched with the hub server. I am confused as to why it would make it to the edge server and get lost in a local loop while sending to the hub server ther is subscribed to the edge server. I end up once the message is bounced with: \Received: from<edge server name>(<public IP>) by<HELOname>(<internal IP>) with Microsoft SMTP Server id 8.1.291.1; Wed, 5 Nov 200813:59:16 -0800 and Received-SPF: None (<edge server name>: tesitngemail@yahoo.com does not designatepermitted sender hosts) I am not sure what I need to do to get the message to the HT. The account that it is intended for when I look at the properties is set to ready and teh message in the queue is always on retry.

Hi, Did you enable some spam checking or something ? It looks like you check the SPF try to disable the spam agents and check again. Is this the only address you have issues with or are there more ? Regards, Johan blog: www.johanveldhuis.nl

Hi Jacob, Please help me gather the following information on the Edge Server to troubleshoot the issue: 1. Run following commands on Edge Server and post the result here: Get-sendconnector |fl Get-accepteddomain |fl 2. Please ping the FQDN of the Hub transport server on the Edge server, please let me know whether you are able to get the correct IP address of the Hub server. 3. Please let me know whether all the inbound email encountered problem or the inbound email from a specific domain encountered the problem. Mike

Hello,I have this same problem in a new Exchange 2007 testing environment. All mail from outside the organization stays in the Q on the Edge Server with error: A Local Loop Was Detected. 1. Here is the output of the following commands: Get-sendconnector |flAddressSpaces : {smtp:*;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : TrueDomainSecureEnabled : TrueEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : NSGCEDGE01Identity : EdgeSync - Default-First-Site-Name to InternetIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Default-First-Site-Name to InternetPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {}SmartHostsString :SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {NSGCEDGE01}UseExternalDNSServersEnabled : False AddressSpaces : {smtp:--;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : TrueDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : NSGCEDGE01Identity : EdgeSync - Inbound to Default-First-Site-NameIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Inbound to Default-First-Site-NamePort : 25ProtocolLoggingLevel : VerboseRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {}SmartHostsString :SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {NSGCEDGE01}UseExternalDNSServersEnabled : TrueGet-accepteddomain |flDomainName : netshopusa.comDomainType : AuthoritativeAddressBookEnabled : TrueDefault : TrueAdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : netshopusa.comDistinguishedName : CN=netshopusa.com,CN=Accepted Domains,CN=Transport Setting s,CN=netshopusa,CN=Microsoft Exchange,CN=Services,CN=Confi guration,DC=netshopusa,DC=comIdentity : netshopusa.comGuid : d81e0cc7-5ccd-4b70-95d3-fb96d26ab9eeObjectCategory : netshopusa.com/Configuration/Schema/ms-Exch-Accepted-Domai nObjectClass : {top, msExchAcceptedDomain}WhenChanged : 2/26/2009 3:26:29 PMWhenCreated : 2/26/2009 3:26:29 PMOriginatingServer : NETSHOPDC.netshopusa.comIsValid : True2. Ping of the Hub Transport Server FQDN resolves the corect IP3. All inbound mail from outside the organization encounters the sam problem. "Non Deliver" messages also spend a long time in the Q, but I eventually get a FAILURE message with a details.txt file like this:Reporting-MTA: dns;netshopusa.comReceived-From-MTA: dns;NSGCEDGE01.netshopusa.comArrival-Date: Wed, 4 Mar 2009 22:31:41 +0000 Final-Recipient: rfc822;pdanieli@netshopusa.comAction: failedStatus: 5.4.6Diagnostic-Code: smtp;554 5.4.6 Hop count exceeded - possible mail loopRemote-MTA: dns;mail.netshopusa.comor a DELAYED message with a ATT#####.txt like this:Reporting-MTA: dns;mail.nsgi-hq.com Final-Recipient: rfc822;name@netshopusa.comAction: delayedStatus: 4.4.7Will-Retry-Until: Fri, 6 Mar 2009 14:50:37 -0500X-Display-Name: name name I have Turned off all Spam filtering, butno fix.Any help would be very much appreciated. Dan

This error seems to have been caused by a certificate mismatch. Removed all certificates from Edge and Hub.Removed subscription.Generated new self-signed certificates on both the Edge and Hub.Created a new subscription.OK